-
Notifications
You must be signed in to change notification settings - Fork 12k
Remove "experimental" from zoneless and add prompt for new apps #30034
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
OOC is there a world where we can have both zones and zoneless in the same project? Asking for the sake of incremental migrations |
No, not for that definition of “incremental”. But you can still incrementally migrate components to be Zoneless compatible. Everything Zoneless also works with zones. Everything in the angular components repo was migrated incrementally to be Zoneless compatible prior to the experimental release in v18. |
Alright, so having only OnPush components, and signals, basically, right? I suppose you'll publish some tips/guides |
https://angular.dev/guide/experimental/zoneless#requirements-for-zoneless-compatibility OnPush, no NgZone.on[Stable/MicrotaskEmpty]. Test with the exhaustive checkNoChanges. It’s surprisingly straightforward. There should be minimal toil for apps written with OnPush. For those that aren’t, that step alone is 90% of the work and 99% of the difficulty. |
Yup, awesome, thanks! |
This commit removes experimental from the option and provider names
This commit adds a prompt to ask if the user wants to generate the app as zoneless.
See individual commits.